第一次看此系列文的朋友，請先移步到 Day 1 – 如何開始？進行方式、自我介紹實戰 哦！

🎬 情境故事

今天進入「模擬全流程面試」！你要想像自己正在參加一場完整的後端工程師面試。從自我介紹、專案分享，到白板題、系統設計、行為題，再到最後提問，都要一次走過。

今日目標：在完整模擬中，檢驗前七天練習的累積成果。

🤖 Config Prompt

[Config]
- Day: Day8 – Full Mock Interview
- Scenario: A complete mock job interview for a backend software engineer role. 
- The session should simulate a real interview from start to finish, including:
  1. Introduction
  2. Project experience
  3. Whiteboard/coding explanation
  4. System design
  5. Behavioral questions (STAR)
  6. Asking questions to the interviewer
- At the end, provide short overall feedback before the Final Report.

👉 在練習之前...

想一下：

1. 自我介紹 — 你的背景與轉職/成長故事
2. 專案經驗 — 需求、角色、技術、成果
3. 白板題 — 有哪些句型可以使用
4. 系統設計 — 如何詢問需求及釐清問題
5. 行為題 — 用 STAR 法則準備一個例子（衝突、挑戰或成就）
6. 最後提問 — 對公司、團隊或角色的問題

並且把關鍵字寫下來。

我的關鍵字：

1. Backend engineer, 3 years, Golang, Performance fine-tuning
2. Optimize the login and register API, main developer, goroutine and MySQL Index, TPS from 600 to 3000+
3. clarify the problem
4. simple concept solution
5. optimizing the api tps from 600 to 3000+
6. what's your expectation of this role for the first year

🎯 開始進行練習

記得把對話錄下來，自己聽一次，想想有哪裡不自然。

🆘 今日救命句

• 救命句：

  Could you please repeat the question?

• 爭取思考時間：

  That’s a good question. Let me think for a moment.

🔑 核心句型

1. 自我介紹

   • I have been working as a backend engineer for three years.
   • Before that, I worked as an animator for five years.

2. 專案經驗

   • I was responsible for optimizing the login API.
   • The performance improved from 600 TPS to 3,000 TPS.

3. 白板題解釋

   • First, I would use a HashMap to check duplicates.
   • The algorithm runs in O(n) time complexity.

4. 系統設計

   • We need to handle high concurrency by using a message queue.
   • To prevent overselling, I would add a lock mechanism.

5. 行為題 (STAR)

   • In that situation, I suggested a new approach and the team accepted it.
   • As a result, the project was delivered on time.

6. 提問

   • What qualities do you value most in this role?
   • How does the team usually collaborate on projects?

📝 我的今日反饋

前幾天練習的都還回去了哭。
今天又重新複習了這幾天的內容，後續需要多練習。

1) Per-turn Corrections:
	•	You said: “The function have to handle the user authoratic?”
Recast: “You mean the function has to handle user authentication, right?”
Alternative: “You mean the function should handle user authentication, correct?”
	•	You said: “We improved the performance from TPS from about 600 to over 3000.”
Recast: “You mean we improved the TPS from about 600 to over 3000.”
Alternative: “We increased TPS from roughly 600 to more than 3000.”

2) Top 3 Patterns:
	•	Plural vs. Singular: Remember to match “the function has” instead of “the function have.” (Rule: Third-person singular uses ‘has.’)
	•	Article Use: Sometimes you missed articles like “a” or “the.” (Rule: Add ‘a’ or ‘the’ where needed for clarity.)
	•	Word Forms: You sometimes mixed forms like “authoratic” instead of “authentication.” (Rule: Double-check the correct noun form.)

3) Phrase Pack:
	•	“I specialize in Golang and performance tuning.”
	•	“We used caching to speed things up.”
	•	“We scaled the system horizontally.”
	•	“Can you tell me what you expect in the first year?”
	•	“We improved throughput from 600 TPS to over 3000 TPS.”
	•	“I worked as the main developer on that project.”
	•	“We focused on optimizing the API performance.”

4) Intonation Tip:
Try stressing key numbers or results, like “We increased it to over three thousand TPS.” Emphasizing numbers helps your listener follow key achievements.

5) Fluency & Pronunciation Notes:
	•	Your pace was nice and moderate—keep that up.
	•	You self-corrected well when you got stuck. Just continue that habit.
	•	Your vowel sounds were clear and easy to understand.
	•	Remember to keep sentences short for clarity.
	•	Good job on using stress on important words.

6) Key Focus for Next Time:
	•	Goal 1: Practice a three-minute drill on explaining project achievements in short sentences.
	•	Goal 2: Do a quick substitution drill with numbers and results to practice intonation.
	•	Goal 3: Summarize a process in under one minute to build brevity.